Repository navigation
ci: deploy releases to the K3s cluster - #6
Merged
Merged
Conversation
Production moved from docker compose on 207.57.124.102 to the K3s cluster (namespace stein-ai, Helm release "multica", database in the shared CloudNativePG cluster pg-main). The deploy-production job now runs `helm upgrade` with the in-repo chart and deploy/k3s/values.yaml, setting only the image tags, then checks the public endpoint. - Add deploy/k3s/values.yaml and deploy/k3s/ingress.yaml (the config that currently runs in the cluster; secrets stay in the multica-secrets Secret) - Replace the sshpass/compose deploy steps; needs repository secret KUBE_CONFIG (namespace-scoped ServiceAccount stein-ai/ci-deployer) - SERVER_IP, SERVER_USER and SERVER_PWD are no longer used Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Production moved from Docker on 207.57.124.102 to the K3s cluster (
k3s.seasonschange.cn) on 2026-11-11. The service is already running there; this PR only changes how releases reach it.Changes
deploy-productionnow runshelm upgrade multica deploy/helm/multica -f deploy/k3s/values.yaml, setting only the image tags. It waits for the rollout, then checkshttps://steinai.tmlab.top/api/configdeploy/k3s/values.yamlanddeploy/k3s/ingress.yaml, the config currently running in the cluster. Secrets stay in themultica-secretsSecretVerification
helm upgrade --dry-run=serverwith these values renders the same manifest as the running release (v0.1.9)stein-aionly and cannot touch other namespacesSecrets
KUBE_CONFIGis set: a kubeconfig for ServiceAccountstein-ai/ci-deployerSERVER_IP,SERVER_USERandSERVER_PWDare no longer used and can be deleted after mergeRollback:
helm -n stein-ai rollback multica🤖 Generated with Claude Code